What

Orders page showed nothing for fresh/wallet-disconnected users because selectedChainIds started as [] and no code ever seeded it.

validChainIds.subscribe only filtered stale entries — it never auto-selected chains for users with an empty selection. Connecting a wallet didn't directly fix this either (the wallet sets chainId, not selectedChainIds). In practice, users only saw orders if they had a prior chain selection persisted in localStorage, which is why the issue correlates with wallet connection: the wallet flow incidentally triggers a chain-selection UI.

Fix

One-line guard in validChainIds.subscribe: when validChainIds first becomes non-empty and selectedChainIds is empty, seed selectedChainIds with all valid chain IDs. Returning users (non-empty selectedChainIds in localStorage) keep their stored selection unchanged.

 validChainIds.subscribe((valid) => {
   if (valid.length > 0) {
     selectedChainIds.update((current) => {
+      if (current.length === 0) return [...valid];
       const filtered = current.filter((id) => valid.includes(id));
       return filtered.length !== current.length ? filtered : current;
     });
   }
 });

Tests

Two new unit tests in settings.test.ts:

• seeds selectedChainIds with all validChainIds when selectedChainIds is empty — fresh-user path
• does not re-seed selectedChainIds when validChainIds updates and selectedChainIds is already set — returning-user path (no clobber)

All seven existing pruning/persistence tests continue to pass.

Closes #2747

Co-Authored-By: Claude noreply@anthropic.com

Summary by CodeRabbit

• Bug Fixes
  • Improved chain selection initialization to automatically populate available chains when no explicit selection exists, while preserving user-selected chains during subsequent updates.